Overview
What is SSIS?
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
SSIS, the must have extension for SSMS
Rapid and low cost integration with various sources for a DW
One of the best on-premise ETL tools
Amazing data warehousing tool
Good for startups or companies with limited data variability, Big data companies will need better tools
Data integration and migration are made easier with this tool.
Trust Microsoft to vanish your data integration troubles
Tool for data integration and migration
SQL Server Integration Services (SSIS) is a winner and helps solve many business problems effectively.
Worth of money
Data processing with SSIS
SSIS, free but not intuitive
Provides value to cost and excellent with MSBI Stack, But needs more features/updates
Great product to consolidate data for SQL Reporting purposes
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Connect to traditional data sources (53)8.888%
- Simple transformations (53)8.585%
- Complex transformations (52)7.777%
- Testing and debugging (48)6.161%
Pricing
What is SSIS?
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
26 people also want pricing
Alternatives Pricing
What is Clear Analytics?
Clear Analytics is a business intelligence solution that enables non technical end users to perform analytics by leveraging existing knowledge of Excel coupled with a built in query builder. Some key features include: Dynamic Data Refresh, Data Share and In-Excel Collaboration.
What is Vertify?
VertifyData is a cloud-based integration platform with core integration capacities, including a drag-and-drop interface and real-time synchronization. It also offers over 80 prebuilt connectors and templates, plus customizable integrations for scaling businesses.
Product Demos
Demonstration of Multicast transformation in SQL Server Integration Services (SSIS)
SSIS Tutorial Part 78- What is Multicast Transformation in SSIS (Quick Demo)
SSIS Tutorial Part 119-Execute SQL Task (Full Result Set) Demo in SSIS Package
SSIS Tutorial Part 72- What is Conditional Split Transformation in SSIS (Quick Demo)
SSIS Tutorial Part 02- How to Load Tab Delimited File To SQL Server Table in SSIS Package
Features
Data Source Connection
Ability to connect to multiple data sources
- 8.8Connect to traditional data sources(53) Ratings
Ability to connect to traditional data sources like relational databases, flat files, XML files and packaged applications
- 6.2Connecto to Big Data and NoSQL(40) Ratings
Ability to connect to non-traditional data sources like Hadoop and other big data technologies, and NoSQL databases
Data Transformations
Data transformations include calculations, search and replace, data normalization and data parsing
- 8.5Simple transformations(53) Ratings
Simple data transformations are calculations, data type conversions, aggregations and search and replace operations
- 7.7Complex transformations(52) Ratings
Complex data transformations are data normalization, advanced data parsing, etc.
Data Modeling
A data model is a diagram or flowchart that illustrates the relationships between data
- 8.6Data model creation(27) Ratings
Ability to create and maintain data models using a graphical tool to define relationships between data
- 7.1Metadata management(33) Ratings
Automated discovery of metadata with ability to synchronize and share metadata with other tools like Master Data Management
- 8.1Business rules and workflow(42) Ratings
Ability to define and manage business rules and workflows
- 7.3Collaboration(38) Ratings
Collaboration is enabled by a shared repository of project information and metadata
- 6.1Testing and debugging(48) Ratings
Tool to debug and tune for optimal performance
Data Governance
Data governance is the practise of implementing policies defining effective use of an organization's data assets
- 7.4Integration with data quality tools(36) Ratings
Integration with tools for cleansing, parsing and normalizing data according to business rules
- 6.5Integration with MDM tools(36) Ratings
Integration with master data management tools to ensure data consistency across the organization
Product Details
- About
- Tech Details
- FAQs
What is SSIS?
SSIS Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(258)Attribute Ratings
Reviews
(1-25 of 29)- SSIS is good for small, simple data syncs.
- SSIS is good for moving data quickly into SQL Server (good batch performance).
- Very hard to diff for code review when changes are made.
- Very buggy IDE (freezes in Visual Studio, doesn't always show what's in the underlying XML properly)
- Lacking lots of features or more modern tools, like ability to monitor for changes to the source schema and apply them to the target.
SSIS, the must have extension for SSMS
- Offers real-time, message-based capabilities
- Tight integration with SQL Server and visual studio
- Ease and speed of implementation
- Standardized data integration
- Sometimes create issues in non-windows environments.
- SSIS lacks support for alternative data integration styles.
- Problematic integration with other products.
- SSIS is an in-memory pipeline. That’s why it’s important to make sure that all transformations occur in memory
- Try to minimize logged operations
- Plan for capacity by understanding resource utilization
- Optimize the SQL lookup transformation, data source, and destination
- Schedule and distribute it correctly
- Easily connect with a wide variety of sources.
- Provide control and flow to job execution order.
- Able to extend functionality through scripting tasks.
- Not flexible when source/target tables and file formats change.
- Inflexible with regards to varying data types when Excel spreadsheets are used as a source or columns are added (as per previous item).
- Occasional issues around mixed development and production x86/x64 run times can be frustrating.
One of the best on-premise ETL tools
- Connect to various sources
- Basic transformations are included
- Connect to various destinations
- We still need plugins to connect to SFTP and other sources. Many vendors in the market give this by default
- It's an ETL tool and the ability to do ELT or ETLTL means spinning up more pipelines and packages
- It still has compatibility issues in Visual Studio 2017
Amazing data warehousing tool
- I am able to use the GIS tools to easily generate solutions without coding.
- Built in tasks that speed up web developing.
- SSIS enables automated data preparations.
- Amazing integration with Microsoft tools.
- Creation of ETL mapping.
- It depends so much on the Microsoft environment and has integration issues with other formats like JSON and Excel.
- Error messages are unclear, this makes us spend a lot of time figuring out what has gone wrong making the debugging process hectic.
Good for startups or companies with limited data variability, Big data companies will need better tools
- Standard ETL use cases for daily loads
- Loading incoming data from Vendors which is placed on FTP and adding them to the SQL Warehouse
- Creating outgoing data files and writing them to Vendor FTPs
- Easy Active Directory integration for seamless connections to SQL Server
- CI/CD by hosting the code on visualstudio.com
- API connections are not a native functionality. We use Zappysys extensions but they work only in certain cases.
- Dependency executions - no simple way to create a hierarchy/chain of executions. Ex: Define if the execution of the child process should be stopped if a parent fails or a certain condition is triggered in the parent process and then redirect to a different part of the chain (think like a flowchart for executions).
Tool for data integration and migration
- Encrypt files with SSIS and send them to various network locations this way we solve complex business problems.
- We can migrate DTS packages to SSIS while choosing to run DTS packages using DTS runtime or incorporate DTS packages into SSIS this way we migrate DTS packages to SQL Server Integration Services.
- We can transform data to make sure it complies with the rules of the database they are migrating to other servers with Integrations Services.
- User-required automation needs much more scope.
- Exporting numerous tables in CSV format has to be done one by one by manual.
SQL Server Integration Services (SSIS) is a winner and helps solve many business problems effectively.
- Create Packages in SQL Server Data Tools
- Reuse Control Flow across Packages by Using Control Flow Package Parts
- Build Integration Services User Interface
- We can improve Integration Services error messages, including a list of most Integration Services errors and their description.
- Improvement to create custom event handlers for these events to extend package functionality.
- Better support for tools and wizards helping with Legacy Package Deployment.
Data processing with SSIS
- Data transfer
- Automation
- Programability
- Scheduling
- Clarity on errors
- Support
Processing data, for ETL, so you can just get the files, using something like FTPs automation and the data will be processed, and then you can just work on your reports or do all the BI needed for the company
Provides value to cost and excellent with MSBI Stack, But needs more features/updates
- FTP Downloads.
- Run 3rd party softwares.
- Intuitive UI.
- Need more connectors/sources/destination components.
- Ability to support not just Microsoft services but others too.
- More updates & new features.
- If the job fails, we are alerted
- It has a easy to use GUI to build projects
- Does well with gathering data from different types of data sets
- Converting flat files of data requires a data transformation that is tedious
SQL Server Express + SSIS basics
- Extraction and convert data from various sources
- Pipelining in the data extraction process
- Unions between different data sources akin one meta datasource
- Some labels in Visual Studio snap-in for MS SQL Server are collapsed on non-English (German & Russian tested) locales.
Less appropriate: big key-value data storages processed slowly, and hard to make data mining through uniting non-RDBMS and RDBMS data sources naive way. The data from non-SQL databases should be prepared accordingly to be represented in a table-like way if possible.
SSIS Just Works
- Process flow.
- Connection to a wide array of sources.
- Built-in upsert component.
- Better operability with source control systems.
1. To populate our data warehouse. Running SSIS packages from the server on a 10-minute schedule, we extract, transform and load the data into the warehouse to support all internal reporting and provide data as a service to our global partners.
2. Bulk data import to our CRM system. Building packages to run on-demand to bulk import structured data to our CRM instance.
In the past, we have used SSIS packages to complete a one-time migration from a legacy CRM system to the current CRM.
- Ease of use - can be used with no prior experience in a relatively short amount of time.
- Flexibility - provides multiple means of accomplishing tasks to be able to support virtually any scenario.
- Performance - performs well with default configurations but allows the user to choose a multitude of options that can enhance performance.
- Resilient - supports the configuration of error handling to prevent and identify breakages.
- Complete suite of configurable tools.
- Connection managers for online data sources can be tricky to configure.
- Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
- Mapping destination using OLE DB command is difficult as destination columns are unnamed.
- Excel or flat file connections are limited by version and type.
- SSIS is particularly well suited for jobs that need to be consistent, repeatable, and error managed.
- Ongoing extract, transform, load [ETL] jobs that are scheduled or manual.
- One-time ETL with complex datasets.
- Migrations of large datasets.
SSIS is not well suited for small or simple datasets that can be copied or exported safely to flat files for import. It is possible to do this but would generally take longer to build in SSIS unless there was a good reason to .remove manual handling of the data in transport or the action needed to be testable/repeatable.
- Almost no programming is needed, like drawing simple flow diagrams.
- If you want to be more advanced you can add some VB or C# programming if needed.
- Microsoft tool using all the great connectors, using any data source
- Easy to add a third part like Cozyroc
- File handling
- Integration with office tools could always be improved, MS, as usual, provides these 80% solutions to make room for third vendors.
- Error message or event handling, better messages and link to processes.
- SSIS works very well pulling well-defined data into SQL Server from a wide variety of data sources.
- It comes free with the SQL Server so it is hard not to consider using it providing you have a team who is trained and experienced using SSIS.
- When SSIS doesn't have exactly what you need you can use C# or VBA to extend its functionality.
- SSIS has been a bit neglected by Microsoft and new features are slow in coming.
- When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
- While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.
SSIS - Strong performer in the traditional data space, but can be improved in handling JSON objects
- Very good for traditional RDBMS ETL and integration.
- Good developer community support online.
- Good at ingesting structured flat files (CSV, TXT, Excel).
- The tool struggles out of the box handling emerging datasets such as JSON feeds.
- Unstructured datasets can be challenging to work with.
- Some out of the box can be very resource heavy, and the UI is not very straight forward. Luckily there's a large community of SSIS users that can provide guidance.
SSIS may not be the best tool if you are using it for ETL and data integrations for JSON and XML feeds. The native tree parser is not very good.
SQL Server Integration Services: a great tool for small to medium sized implementations
- It handles SQL Server databases flawlessly
- It provides a robust developer interface
- It allows a developer to encapsulate complex scripts directly within an SSIS project or reuse scripts across projects
- It interfaces quite well with a large number of available libraries
- SSIS memory usage can be quite high particularly when SSI and SQL server are on the same machine
- SSIS is not available on any environment other than Microsoft Windows
- SSIS does not function with any database engine back-end other than Microsoft SQL Server
- Source systems connectivity (RDBMS, Flat Files etc)
- Embedding SQL and other code in case of complex business logic and data transformations
- Multitude of data transformation options
- Ease of use, easy to learn
- Skills availability in the market
- version control/configuration management
- Programmatic issues like NULL handling (it's RDBMS counterpart SQL Server database uses NULL differently)
- The source connectivity options should be enhanced
A solid ETL tool. Data doesn't stay in one place, SSIS keeps it going where it needs to go.
- There are many good workflow tools and ways to control the order in which things happen. In a short amount of time, you can quickly create a package that will move data from point A to point B and have it scheduled to run 4 times a day. Or if you need error handling or other business logic, you can spend more time and completely automate repetitive tasks. Robust? Check!
- SSIS can consume multiple sources of data. From flat files, to Excel, to Oracle, or DB2...I've been able to access multiple data types and move them in and out of SQL databases with SSIS. We had one linux system that ran a Basis database system and there was a need to have something done, but no one could figure out how to make it work. I was able to use SSIS to import files and execute code on a server that had nothing to do with SQL server. So flexible? Check!
- We already use SQL server almost exclusively for our enterprise database needs. The fact that we already have access to this tool at no additional cost to the business is a bonus. The fact that it is powerful, even better. Value? Check!
- I know in my "pros" comments, I said it was nice because we already had access to SSIS by virtue of being able to install it on existing SQL servers with no additional license cost. But, if you rely heavily on SSIS, you will want to have it on its own server rather than letting it share resources with a very active SQL server. That means additional licenses. It can consume a lot of resources, depending on the amount of data you're pushing through SSIS at any given time.
- Current versions of SSIS do a much better job of managing deployment of packages into production. It used to be an all-or-nothing proposition so if you had to make a small change to a project that had many packages in it, you'd have to redeploy the entire project which means lots of extra testing. The introduction of package level deployment was welcome.
- SQL server and SSIS play very well together when they have enough resources. If you're using virtual servers and can add CPU/RAM/Space easily, then by all means, put them together and manage the resources so they stay out of each other's way. If you don't have the capability to do that, then you'd be better off having SSIS on a separate server. When everything is working well, it is amazing. But if you make SSIS and SQL fight over resources, it's not pretty (SQL wins that fight by the way in case you were wondering!)
- If I'm being honest, I haven't had to point SSIS to a huge variety of source systems. It could be that SSIS doesn't play well with certain DBMS' (I've heard Sybase compatibility complaints before) and you'll need to do some research and testing before actually using it in production.
Great ETL tool
- Great for parsing data from various file formats into SQL server. As an example, we use it to extract data from XML, EDI and other flat files.
- Great for applying custom business logic in the ETL process. These business logic could be built into functions, stored procedures and applied through the SSIS packages.
- I like it's exception handling capabilities and how it's able to show the module that threw up the exception by highlighting it in red.
- Works very well with Visual Studio and as a matter of fact, you can build all your SSIS packages right from SQL without even opening up SQL server or BIDS.
- Not sure if it has JSON support but if it does, that would be awesome! Basically, the ability to consume data from a JSON data set.
- In as much as Microsoft built it for the SQL database, it would be awesome if we could leverage SSIS for data ETL into other databases like MySQL and Oracle etc.
- Add more color themes! The default color theme is old school and really sucks if you ask me.
2. Amazing if your primary database environment is SQL server.
3. Works great with Visual Studio and Microsoft even has it now on the Azure platform.
4. Works great with various file formats - XML, EDI, spreadsheets, flat files etc.
5. Works great in scenarios where it is necessary to apply business logic through stored procedures etc.
SSIS offers what I need for data processing.
- Presents the flow of data processing very well, making it easy to learn/understand SSIS packages.
- T-SQL and C# friendly.
- Comprehensive configuration, logging, and error handling.
- Some components are not working very well, including sorting, SCD, etc.
- Different components could have different syntax or data type definition.
- Not enough scripting learning materials.
SSIS Addict
- Native data connections to SQL Server and Azure SQL DB and DW
- Flat file processing
- .NET C#/VB scripting
- Ease of use in designing and implementing control flows within conditional processing and looping
- Integration with Access/Excel should be more seamless and less problematic
- CASS certified address standardization
- Higher performing Slowly Changing Dimension functionality
- SFTP
- Incremental loading (deletion, upsert, etc.)
- PowerBI integration. I really really really want to be able to refresh reports via IS packages
- More Azure administration tasks
- Office365 and Sharepoint integration
- Full refresh loading files (Excel and Flat File) into SQL Server.
- Integrating .Net (VB/C#) scripting
- Incremental loading
- OLAP database loading
- Streaming, real-time/near real-time loading
- Big data loading
Use it if you have a Microsoft Stack
- Clear GUI and ETL workflow. It's very easy to understand how the data is being managed. When pulling up a SSIS solution that someone else has created, it's very easy to see what's going on-- how the data is extracted, how it is transformed, and how it's being loaded.
- Deploying scripts. Once a proper package store is configured, you just need to hit deploy and it handles the rest. It's also flexible enough that you can still use SSIS packages without using an SSIS DB for version control by calling them through the file system. Or if you're one of those people who love batch scripts, you can also execute the packages through command line.
- SSIS Package Store. It's a great way to manage your versions and deployments. Bonus is that if you use a package store, it'll also give you error reports after the fact if a package fails for debugging. It'll tell you exactly what step failed and why.
- I think it handles undefined/dynamic data sources poorly. Considering that we use it primarily to ETL data from other systems across the whole organization to bring into our BU's data warehouse, we sometimes have issues when the source has changed. If someone adds a column without letting us know, we'll need to modify the SSIS packages.
- Sometimes the error codes are vague or cryptic. When debugging a SSIS package I have to google the code or error message and hope someone has a similar issue on stack overflow.
- SSIS really only works if you're already using a lot of Microsoft Products like Microsoft SQL Server or SQL Server Reporting Services. As mentioned in the name of the application, "integration services", it's designed to integrate your products together so that you can get the most out of it.
SSIS - Our go to ETL Tool
- Handling upsert functionality (i.e. performing lookups against existing data to determine new versus existing records).
- Automation of scheduled file imports. Essentially any consistent data source can be automated after a one-time SSIS package is set up.
- Ability to handle a wide variety of data sources.
- Excel data type handling - makes assumptions on a single data type where there might be multiple data types in a specific column.
- Better handling of data schema changes - If you have column changes or additions in your data source, it does not always implicitly make those changes across all data transformation tasks within the package.
- No reliable built-in functionality for SFTP connections.